Visualizers for change management system

ABSTRACT

A change management system may use a phased status indicator that may illustrate several phases of a change request and a current status for each phase of a change management lifecycle. Additionally, a group of change requests may be displayed in a linked manner showing various relationships between change requests. The status indicator and linked display may be used together or separately to illustrate the status of various change requests and within interactive displays of change request data.

BACKGROUND

Change management systems may be used by Information Technologydepartments to track various modifications, upgrades, or changes to manydifferent components within an information technology infrastructure.Because many components are interrelated with each other, changes thatare deployed in an information technology infrastructure may have manyinterrelated effects that may be related to other changes.

Many change management systems may use a change request or other vehiclefor proposing, approving, and implementing changes. A process forhandling change requests may be defined to progress through variousstages, and during each stage, the change request may have differentstates.

As change management systems are deployed, the quantity of changerequests may produce large amounts of data. These data may be difficultto quickly comprehend and visualize when presented in tabular orcolumnar formats.

SUMMARY

A change management system may use a status indicator to illustrate thelifecycle phases of a change request and the status of an individualchange request in that lifecycle. Additionally, a group of changerequests may be displayed in a linked manner showing variousrelationships between change requests. The status indicator and linkeddisplay may be used together or separately to illustrate the status ofvarious change requests and within interactive displays of changerequest data.

This Summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This Summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended tobe used to limit the scope of the claimed subject matter.

BRIEF DESCRIPTION OF THE DRAWINGS

In the drawings,

FIG. 1 is a diagram illustration of an embodiment showing a changemanagement system.

FIG. 2 is a flowchart illustration of an embodiment showing a method fordefining icons.

FIG. 3 is a flowchart illustration of an embodiment showing a method forcreating sequential status icons for a particular change managementitem.

FIG. 4 is a diagram illustration of an embodiment showing a changemanagement process and icons that may be used to illustrate the statusduring the process.

FIG. 5 is a flowchart illustration of an embodiment showing a method forcreating a graphical representation of change management items.

FIG. 6 is a diagram illustration of an embodiment showing a graphicalrepresentation of several change management items.

DETAILED DESCRIPTION

Visualization tools within a change management system may be used toinstantly convey the status of a change request as well as viewinterrelated change requests. Such tools may be used in many differentareas, such as interactive displays within a change management system aswell as email or other items that contain change management information.

The status of a single change request may be illustrated by a series oficons that represent the lifecycle of a change request. Each icon mayhave a status indicator that may visually show the status of the changerequest. Since the change request may have a current phase and status,an icon representing a completed stage or a stage yet to be completedmay be shown with the current status of the current phase icon.Completed and future stages may be illustrated with grayed-out icons oricons with a different color to differentiate from the current phase andstatus.

The change request status indicator may be presented any place a changerequest may be referenced. For example, a list of existing changerequests may be shown in tabular form with multiple change requests andtheir corresponding icons. References to change requests in documents oremails may include a status indicator.

In some cases, a status indicator may be interactive, allowing a user tomouse over, click on, right click, or otherwise interact with the statusindicator to perform certain functions that may be available or todisplay underlying data or for other actions.

The status of multiple change requests may be illustrated by showingvarious change requests and relationships between the change requests.The relationships may be one way or two way relationships between changerequests, in addition to sequential, parallel, peer to peer,parent/child, or other relationships. In some cases, such a display maybe interactive, enabling a user to view, edit, or otherwise interactwith change requests or relationships as independent entities or asgroups of entities.

Specific embodiments of the subject matter are used to illustratespecific inventive aspects. The embodiments are by way of example only,and are susceptible to various modifications and alternative forms. Theappended claims are intended to cover all modifications, equivalents,and alternatives falling within the spirit and scope of the invention asdefined by the claims.

Throughout this specification, like reference numbers signify the sameelements throughout the description of the figures.

When elements are referred to as being “connected” or “coupled,” theelements can be directly connected or coupled together or one or moreintervening elements may also be present. In contrast, when elements arereferred to as being “directly connected” or “directly coupled,” thereare no intervening elements present.

The subject matter may be embodied as devices, systems, methods, and/orcomputer program products. Accordingly, some or all of the subjectmatter may be embodied in hardware and/or in software (includingfirmware, resident software, micro-code, state machines, gate arrays,etc.) Furthermore, the subject matter may take the form of a computerprogram product on a computer-usable or computer-readable storage mediumhaving computer-usable or computer-readable program code embodied in themedium for use by or in connection with an instruction execution system.In the context of this document, a computer-usable or computer-readablemedium may be any medium that can contain, store, communicate,propagate, or transport the program for use by or in connection with theinstruction execution system, apparatus, or device.

The computer-usable or computer-readable medium may be, for example butnot limited to, an electronic, magnetic, optical, electromagnetic,infrared, or semiconductor system, apparatus, device, or propagationmedium. By way of example, and not limitation, computer readable mediamay comprise computer storage media and communication media.

Computer storage media includes volatile and nonvolatile, removable andnon-removable media implemented in any method or technology for storageof information such as computer readable instructions, data structures,program modules or other data. Computer storage media includes, but isnot limited to, RAM, ROM, EEPROM, flash memory or other memorytechnology, CD-ROM, digital versatile disks (DVD) or other opticalstorage, magnetic cassettes, magnetic tape, magnetic disk storage orother magnetic storage devices, or any other medium which can be used tostore the desired information and which can accessed by an instructionexecution system. Note that the computer-usable or computer-readablemedium could be paper or another suitable medium upon which the programis printed, as the program can be electronically captured, via, forinstance, optical scanning of the paper or other medium, then compiled,interpreted, of otherwise processed in a suitable manner, if necessary,and then stored in a computer memory.

Communication media typically embodies computer readable instructions,data structures, program modules or other data in a modulated datasignal such as a carrier wave or other transport mechanism and includesany information delivery media. The term “modulated data signal” means asignal that has one or more of its characteristics set or changed insuch a manner as to encode information in the signal. By way of example,and not limitation, communication media includes wired media such as awired network or direct-wired connection, and wireless media such asacoustic, RF, infrared and other wireless media. Combinations of the anyof the above should also be included within the scope of computerreadable media.

When the subject matter is embodied in the general context ofcomputer-executable instructions, the embodiment may comprise programmodules, executed by one or more systems, computers, or other devices.Generally, program modules include routines, programs, objects,components, data structures, etc. that perform particular tasks orimplement particular abstract data types. Typically, the functionalityof the program modules may be combined or distributed as desired invarious embodiments.

FIG. 1 is a diagram of an embodiment 100 showing a change managementsystem. Embodiment 100 may be used to manage changes in an informationtechnology or other application, such as engineering change managementfor product development, project change management for civil engineeringor construction projects, management of legislative or rule makingprocesses, or other uses for change management processes. For thepurposes of example, a change management process for informationtechnology will be discussed throughout this specification, but anyreferences to such a system shall be taken as exemplary and not aslimiting.

A change management system may be used to create change requests,approve change requests, manage changes during implementation, andprovide for review of completed changes. In many cases, change requestsmay be linked together. For example, a sequential relationship may bedefined between two change requests so that one change request isimplemented before another.

In large systems where many changes are managed, the number of changerequests may be very large. In order to effectively communicate changerequest status and the interrelationships between change requests,various visual representations may be used. One example may be a set ofsequential status icons that are arranged in order of phases of alifecycle of a change request. Each of the icons may represent one phaseof the lifecycle and may have an indicator for the current status withinthe phase. Such a visual representation may help a user quickly graspthe current status for an individual change request.

Another example of a visual representation may be a graphical view ofchange requests and the relationships between change requests. Multiplechange requests may be viewed in such a representation, and, in somecases, interactive features on the representation may enable a user toperform various actions directly from the visual representation.Examples of such actions may be to display additional details, editunderlying data, or other functions.

The change management system of embodiment 100 may be configured in manydifferent manners. In the embodiment 100, a client server architectureis illustrated that includes a server 102 that interfaces with a changemanagement database 104. Multiple clients 106 and 110 may interface withthe server 102. Client 106 may have a display device 108. Similarly,client 100 may have a display device 112.

In some instances, a client may interface with the server 102 by runningan application on a client device. The application may communicate withthe server 102 to transfer data to and from the database 104. In such acase, a rendering system 116 may be operable on the client device 110 toanalyze change management data and create visual representations of thedata.

In other instances, a client may interface with the server 102 byrunning a thin client, browser, or other architecture whereby the server102 may perform many of the functions of the overall system. In such aninstance, a client device 106 may use a web browser to send and receiveinformation to a change management application that operates on theserver 102. Many of the functions of a change management application maybe performed on the server 102 in such a case, such as having arendering system 114 that may create visual representations that aretransferred to the client 106 and displayed on the display device 108.

Many different architectures are possible for a change managementsystem. Some systems may have some functions that are performed on aclient device while other functions may be performed by a server. Insome systems, a single computing device may perform all of the changemanagement functions.

In some embodiments, the server 102 and clients 106 and 110 may beconnected by a local area network. In other embodiments, one or both ofthe clients 106 or 110 may access the server 102 through an internetconnection or other wide area network. In some cases, the server 102 mayprovide a change management service that is accessible through a webbrowser as a web service.

FIG. 2 is a flowchart illustration of an embodiment 200 showing a methodfor defining icons that may be used in a sequential status iconrepresentation of a change management item.

A set of sequential stages may be defined for a process in block 202.The sequential stages may be any series of phases, stages, or sequenceby which a process may be executed. For example, a change request mayhave stages defined for preliminary activities, approval phase,execution phase, and completion/wrap up phase. Each embodiment may havedifferent definitions of a phase, stage, or sequence by which a processis executed.

The sequential stages may be defined for any process for which agraphical representation may be desired. The processes may be as diverseas a manufacturing process, a business process, a sales process, or anyother type of sequential process or method that may be defined instages.

For each stage in block 204, a status icon may be defined representing apossible status within the stage or phase in block 206. In some cases,the status icon may be designed to represent the current stage and aspecific status. For example, a completed status may have a green circlewith a check mark over an icon that may represent the stage. A stoppedstatus or halted status may include a stop sign icon. Each stage mayhave a completed status icon and a not-started status icon, in additionto other status icons that may be defined for appropriate status optionsfor a stage.

FIG. 3 is a flowchart diagram of an embodiment 300 showing a method forcreating sequential status icons. Embodiment 300 may be used to create asequence of status icons that illustrate the current status of an item,such as a change control item.

A change control item is selected in block 302. The change control itemmay be a change request or other item within a change management systemfor which a visual status indicator is desired.

For each stage of the lifecycle in block 304 as defined in block 202above, a status icon may be assigned. If the stage has not started inblock 306, the not-started icon may be selected in block 308. If thestage has started in block 306 by is not in process in block 310, acompleted icon may be selected in block 312. If the current stage is inprocess in block 310, a status icon corresponding to the current statusis selected in block 314.

The selected status icons may be grouped in block 316 by the overallsequence. A single entity may be created in block 318 with all of theselected icons and displayed in block 320.

An example of a representative process and the various status icons isshown in the discussion of FIG. 4.

FIG. 4 is a diagram illustration of an embodiment 400 showing a changemanagement process 402 and corresponding sequential icon representations404. Embodiment 400 is merely an example of how a sequence may bedefined into phases or stages, and icons representing various statussituations within the stages may be defined and illustrated.

Embodiment 400 shows a change management process that can be defined infour stages or phases: the first phase 406 is change request generationin block 408. The second phase 418 is an approval phase, while phasethree 446 is an implementation phase, and phase four 474 is a reviewphase.

For each phase, a group of status icons may be defined. When the statusicons are properly selected and presented, the current status of achange request may be visually determined. Because an icon is used foreach phase of the change request lifecycle, the status may be presentedin the context of a timeline for the change request. For example, astatus illustrated in the third icon may visually illustrate that thechange request has progressed to the third phase, with the icon of thethird phase showing the current status.

The first phase 406 may contain a single step, such as generate changerequest 408. The status icons for this phase may be icons 410,illustrating the first phase with a check mark for completed, as well asicons 412, 414, and 416 representing phases two, three, and four,respectively. Icons 412, 414, and 416 may be ‘grayed out’ to representthat the phases have not yet been started.

Each embodiment may have different icons or schemes for visuallyrepresenting a particular phase and the status of the phases. Inembodiment 400, icons representing a particular phase may have a numberthat represents the phase. Other embodiments may have a graphical iconthat may represent a particular phase. In some embodiments, the stageicons may be similar or even the same icon, with the represented stagebeing defined by the position of a particular icon within a sequence oficons.

The second phase 418 may be the approval phase of the change requestlifecycle. During the approval phase, the change request may be sent toreviewers in block 420 who may disposition the change request in block422. The reviewers may approve the change request 424, put the changerequest on hold 426, or reject the change request 428 and notify therequester in block 430 and stop the process in block 432.

The status options within the second phase 418 may be in review, onhold, approved, or rejected. The icons that may be used to representstatus during the second phase may be the completed first phase icon434, and several status icons for the second phase.

The second phase status icons may include an in process status icon 435,an on-hold status icon 436, a rejected icon 438, and a completed icon440.

When the second phase status icons are displayed, the not-started iconsfor the remaining phases may be displayed as icons 442 and 444.

The third phase 446 may be the implementation phase of a change request.The activity owner may be notified in block 448 to perform the task. Theactivity owner may be the actual person who may perform an actiondefined in the change request. If the person performs the activity inblock 450, the activity is in process in block 451. When the activity iscomplete in block 452, the requester may be notified in block 454. Ifthe activity owner does not perform the activity in block 450, theperson may hold or cancel the activity in block 456. If the activity iscancelled in block 456, the requester is notified in block 458 and theprocess may end in block 460. Otherwise, the activity may be placed onhold in block 456.

Based on the actions in the third phase 446, the possible status may bein process, on hold, complete, and cancelled. The icons that may be usedto represent status during the third phase may be the completed icons462 and 464 of the first and second phase, respectively, and the variousicons representing the status of the third phase.

The third phase status icons may include an in process icon 466, apaused or hold icon 468, a completed icon 470, and a cancelled icon 471.

When the third phase status icons are displayed, the not-started icon472 representing phase four may be shown.

The fourth phase 474 may be the review phase of a completed changerequest. If a review is needed in block 476, a review is performed inblock 480 and the process may end in block 478. Otherwise, the processmay end in block 478.

The possible status of phase four may be in process and completed. Theicons representing phase four activities may include completed icons482, 484, and 486 for the first three phases, as well as an in processicon 488 and a completed icon 490.

Embodiment 400 is merely an example of how a complex lifecycle orprocess may be defined into phases and the status of the process may beillustrated by a sequence of icons representing the phases.

In many embodiments, the status of an item may be illustrated withseveral sequential icons. By having a separate icon for each phase, avisual image of the progress through a process may be shown.

Each embodiment may have different manners in which the sequential iconsmay be displayed. In embodiment 400, the icons may be illustrated insequence horizontally from left to right. Other embodiments may arrangeicons vertically from top to bottom or from bottom to top, or evenhorizontally from right to left. Still other embodiments may layout theicons on an angle or along a circuitous or tortuous path.

The icons illustrated in embodiment 400 are shown as distinct, separateicons. Some embodiments may graphically join icons together so that theypresent a single graphical image.

In some embodiments, the various icons may be presented with interactivemechanisms by which a user may perform various actions. For example, astatus icon may have a link to a dialog box or other interactivecomponent whereby a user may view related information, edit someunderlying data, or perform some other action.

FIG. 5 is a flowchart illustration of an embodiment 500 illustrating thecreating of a graphical representation of several related changerequests. Embodiment 500 is another example of visual expressions ofchange requests, with the emphasis on illustrating the relationshipsbetween change requests.

In many embodiments, a change request for a complex or sometimes asimple change may have ripple effects with other managed assets orrelated items within the change management system. In such a situation,additional change requests may be created to address the changes to therelated assets. The additional change requests may be liked byrelationships.

Change requests may be defined with many different types ofrelationships. A sequential dependent relationship may define one changerequest that may be implemented after a first change request iscompleted. A parallel relationship may define two or more changerequests that may be performed in parallel.

Some embodiments may have parent/child relationships or otherhierarchical types of relationships. Some parent/child relationships mayinclude a series of child change requests that make up a parent changerequest. In such cases, the status of the parent change request may rollup the status of the various child change requests.

Some relationships may be defined as one-way relationships where asecond change request may be dependent on a first change request, or asa two-way relationship where each change request is dependent on aportion of the other.

Each embodiment may have different manners of defining relationships andsuch relationships may have different functions or operate in variousways. The relationships discussed in this specification are merelyexamples of some of the ways relationships may be defined and used.

A set of change management items may be received in block 502. Thechange management items may include change requests as well as otheritems such as assets, personnel, or other items that may be displayed.

For each change management item in block 504, at least one relationshipmay be identified in block 506 between the current item and anotheritem.

After identifying the existing relationships, the change managementitems may be arranged in a graphical manner in block 508, and agraphical representation of the change management items with therelationships may be created in block 510.

For each change management item and each relationship in block 512, aset of actions that may be performed on the item or relationship may beidentified in block 514 and an interactive mechanism may be incorporatedinto the graphical representation in block 516.

The graphical representation is displayed in block 518.

Embodiment 500 illustrates a method for composing an interactive diagramthat may show various change management items and the relationshipsbetween the items. Within the graphical representation, variousinteractive features may be placed so that a user may interact with thevarious illustrated components and relationships between the components.

FIG. 6 is a diagram illustration of an embodiment 600 showinginteractive diagrams. Embodiment 600 is an example of how change ordersor other items may be displayed using relationships. Other embodimentsmay use different features, layout techniques, indicators, buttons,graphical elements, or other devices to illustrate change managementitems and the relationships between the items.

In window 602, several change orders are illustrated. A first changeorder 604 is illustrated with a set of sequential status icons 606 and acurrent status icon 608.

In the embodiment, the first change order 604 may be a parent changeorder that may include child change orders 610, 612, and 618. In thisembodiment, a parent change order may act as an aggregation of one ormore child change orders. Because of the parent/child relationship, theicons 606 and 608 may illustrate the aggregated status of the variouschild change requests.

The patent/child relationship may be illustrated by the dashed line 614.Some embodiments may illustrate different types of relationships bydiffering line weights, colors, line types, and other graphicalelements.

Relationship 615 may indicate a two-way dependency between changerequests 610 and 612. The two-way dependency 615 may be defined in amanner that portions of change request 610 depend on portions of changerequest 612 and vice versa.

Change request 618 may have a sequential dependency on both changerequests 610 and 612, as illustrated by solid line 616.

Change request 618 may be a parent change request to several otherchange requests as shown in window 620. The window shows a parent changerequest 622 and several child change requests 624.

The embodiment 600 may have several interactive features built into thedisplay. In some cases, a hot zone or other area may be defined over achange request, an icon within a change request, a relationship, orother areas around the windows 602 and 620 where a cursor may be used tointeract with an item. In some cases, a mouse-over action, selectingaction, right-click action, or any other interaction may trigger a menuof available actions or other interactive feature.

The interactive features may allow a user to perform many differentfunctions of a change management application directly from theinteractive interface of windows 602 or 620.

The foregoing description of the subject matter has been presented forpurposes of illustration and description. It is not intended to beexhaustive or to limit the subject matter to the precise form disclosed,and other modifications and variations may be possible in light of theabove teachings. The embodiment was chosen and described in order tobest explain the principles of the invention and its practicalapplication to thereby enable others skilled in the art to best utilizethe invention in various embodiments and various modifications as aresuited to the particular use contemplated. It is intended that theappended claims be construed to include other alternative embodimentsexcept insofar as limited by the prior art.

What is claimed is:
 1. At a computer device, the computer deviceincluding a display, a method for visually conveying status for amulti-stage change management item, said method comprising: accessingchange management data for said multi-stage change management item froma change management database, said multi-stage change management itemdefining a plurality of stages for a process; in response to accessingthe change manage data, for each stage in said plurality of stages:assigning a stage identifier icon for said stage; defining a completedstatus icon to display along with said stage identifier icon to visuallyindicate that said stage has completed; defining a not yet startedstatus icon to display along with said stage identifier icon to visuallyindicate that said stage has not yet started; for at least one stage insaid plurality of stages, defining one or more additional iconsdisplayable along with said stage identifier icon for said at least onestage, each of said one or more additional icons for visually indicatinga corresponding additional status for said at least one stage when saidat least one stage is the current stage; the computer device analyzingsaid change management data to identify a current stage for saidmulti-stage change management item and to identify a current status forsaid current stage; the computer device forming a set of stageidentifier icon and status icon combinations representing the state ofthe multi-stage change management item, including: assigning a statusicon corresponding to said identified current status to said stageidentifier icon for said identified current stage; assigning saidcompleted icon to said stage identifier icon for any completed stages;and assigning said not yet started icon to said stage identifier iconfor any stages that have yet to be started; and displaying said set ofstage identifier icon and status icon combinations at said display tovisually convey the state of the multi-stage change management item. 2.The method of claim 1 further comprising grouping said set of stageidentifier icon and status icon combinations into a single graphicalelement.
 3. The method of claim 1 further comprising: identifying atleast one activity for said set of stage identifier icon and status iconcombinations; and providing a mechanism by which a user may perform saidactivity by interacting with said set of stage identifier icon andstatus icon combinations.
 4. The method of claim 3, said mechanismcomprising interacting with at least a portion of said sequential statusicons.
 5. The method of claim 1, wherein defining one or more additionalicons to display along with said stage identifier icon comprisesdefining: an in process status icon, an on-hold status icon, and arejected icon.
 6. The method of claim 1, wherein analyzing said changemanagement data to identify a current stage for said multi-stage changemanagement item and to identify a current status for said current stagecomprises identifying one of said at least one stages as the currentstage; and wherein assigning a status icon for said identified currentstatus to said stage identifier icon for said identified current stagecomprises assigning one of the additional status icons to said one of atsaid at least one stages.
 7. A system comprising: a change managementdatabase comprising change management items; a display device; and arendering system adapted to: access change management data for amulti-stage change management item from a change management database,said multi-stage change management item defining a plurality ofsequential stages for a process, stages in the plurality of sequentialstages representing a lifecycle for the multi-stage change managementitem, the lifecycle to be performed sequentially in a defined order froma first stage to a last stage; for each stage in said plurality ofsequential stages: assign a stage identifier icon for said stage; definea completed status icon to display along with said stage identifier iconto visually indicate that said stage has completed; define a not yetstarted status icon to display along with said stage identifier icon tovisually indicate that said stage has not yet started; for one stage insaid plurality of stages, define one or more additional status iconsdisplayable along with said stage identifier icon for said one stage,each of said one or more additional icons for visually indicating acorresponding additional status for said one stage when said one stageis the current stage; analyze said change management data to identify acurrent stage for said multi-stage change management item and toidentify a current status for said current stage; form a set of stageidentifier icon and status icon combinations representing progressionthrough the lifecycle, including: assigning a status icon for theidentified current status to said stage identifier icon for saididentified current stage; assigning said completed icon to said stageidentifier icon for any completed stages; and assigning said not yetstarted icon to said stage identifier icon for any stages that have yetto be started; and render said set of stage identifier icon and statusicon combinations at said display to visually convey the progressionthrough the lifecycle.
 8. The system of claim 7 further comprising: aninteractive display adapted to: display said set of stage identifiericon and status icon combinations; identify an action relating to one ofsaid change management items; and provide an interactive mechanism bywhich a user may perform said action by interacting with a portion ofsaid set of stage identifier icon and status icon combinations thatcorresponds with said one of said change management items.
 9. The systemof claim 8, said change management items comprising change requests. 10.The system of claim 8, said change management items comprisingrelationships.
 11. The system of claim 10, said relationships comprisingat least one of a group composed of: a sequential dependency; a paralleldependency; a parent/child dependency; and a hierarchical dependency.12. At a computer device, the computer device including a display, amethod for visually conveying status for a set of multi-stage changemanagement items, said method comprising: accessing change managementdata for said set of multi-stage change management items, said set ofmulti-stage change management items having at least one relationshipdefined between different change management items, each multi-stagemanagement item in said set of multi-stage change management itemsdefining a plurality of stages for a process; for each multi-stagemanagement item: for each stage in said plurality of stages: assigning astage identifier icon for said stage; defining a completed status iconto display along with said stage identifier icon to visually indicatethat said stage has completed; defining a not yet started status icon todisplay along with said stage identifier icon to visually indicate thatsaid stage has not yet started; for at least one stage in said pluralityof stages, define one or more additional status icons displayable alongwith said stage identifier icon for said at least one stage, each ofsaid one or more additional icons for visually indicating acorresponding additional status for said at least one stage when said atleast one stage is the current stage; the computer device analyzing saidchange management data to identify a current stage for said multi-stagechange management item and to identify a current status for said currentstage; and the computer device forming a set of stage identifier iconand status icon combinations representing the state of the multi-stagechange management item, including: assigning a status icon for theidentified current status to said stage identifier icon for saididentified current stage; assigning said completed icon to said stageidentifier icon for any completed stages; and assigning said not yetstarted icon to said stage identifier icon for any stages that have yetto be started; and displaying said sets of stage identifier icon andstatus icon combinations at said display to visually convey the state ofand relationships between the set of multi-stage change managementitems.
 13. The method of claim 12 further comprising: identifying anaction relating to one of said change management items; and providing aninteractive mechanism by which a user may perform said action byinteracting with a portion of said displayed sets of stage identifiericon and status icon combinations.
 14. The method of claim 13, saidinteractive mechanism comprising using a pointing device.
 15. The methodof claim 12, said change management items comprising change requests.16. The method of claim 12, said change management items comprisingrelationships.
 17. The method of claim 16, said relationships comprisingat least one of a group composed of: a sequential dependency; a paralleldependency; a parent/child dependency; and a hierarchical dependency.18. The method of claim 12, said displayed sets of stage identifier iconand status icon combinations comprising status indicia for at least oneof said change management items.
 19. The method of claim 12, whereindefining one or more additional icons to display along with said stageidentifier icon comprises defining: an in process status icon, anon-hold status icon, and a rejected icon.